Category: Geeks r Us
Hey guys, I am trying to forward ports on an actiontech rowder. I'm sorta getting the hang of how to do it, but I could really use some help. I'm trying to forward port 8000. I go into the firewall page, then port forwarding, then go to the add link. When it asks for my IP, i put in my IP, 192.168.1.x, then go down, and say add a custom rule. I put in the port I'd like to forward 8000 and the name for it, Icecast. Now, Squiggles ran a port scan on me, to make sure I did everything correctly. He says its not coming up when he runs it. What I don't understand is, I had to forward port 21, and that one worked fine, and I'm taking the samd steps to forward 8000, and its not working. If anyone has an actiontech rowder, or has worked with one, can u please call me on skype, or post here? Thanks a lot, Mike.
Since these off brands like action tech or westel are mainly used with isps, it is hard to find anyone who has good experience with these do to accessibility.
Mike allowed remote access into his rotuer for me and here is what i had done. When I run a scan for whatever reason it doesn't show up, but it works anyway.
In the forwarded ports list, there were 2 things forwarded to 8000. Thinking that maybe there might have been a conflict i deleted the custom rule made here. Then, I went into the the shoutcast rule, and there had already been an additional port there named application, that mike had done manually for 8001. I changed that name from application, to shoutcast-incoming and set the protocol type to udp since 8001 as wel know is the outbound audio from his server. It wouldn't make sense for tcp, so we select UDP. Next there is a list for ports. It was set to any, so I arrowed down to change it to range. It then brought up some additional fields I entered 8000 and 8001 in the first set then in the second set I enntered the same thing. If I missed anythign it is still in the router.
But now that I think about it. I'm not so sure the ports were the problem at all. We didn't have shoutcast configured correctly. There were port/IP addressing issues within shoutcast itself. So with this I think that the router may not have even been the issue.
For those who use one of these home routers they are quite a pain and it is rare that you find one that is accessible like a belkin or a linksys. I can see how one could get lost in that router because you have to go down 700 pages of fluf screens just to get to the port forward screen, and it is sort of graphical. It is one of those rely on the alt tags in the images in links to help you.
Lets hope I don't have to do any port forwarding for a while then. I forwarded 21, and the shoutcast server is set up, so unless I absolutely need to, I really don't wanna screw with that.